Seagate/Irwin Minicartridge (mc) Floppy Tape Driver v4.0.0s for Interactive Unix 3.2 Release 4.1 =========================================================== There are two files used install the driver. mc400s_i.txt: (this file) contains a procedure to install the minicartridge tape driver on an Interactive Unix 3.2 Release 4.1 operating system. mc400s_i.Z: (a separate file) contains the corresponding tape driver and supporting utilities. Contents -------- History Controller Support Drive Support Cartridge Support Creating an Installation Floppy Diskette Using sysadm and kconfig to Install the Minicartridge Driver Rebooting After Minicartridge Driver Installation The "mcart" Utility No-rewind Device: /dev/mc/nrmc0 (For Advanced Users) Notes Alternate Tape Controllers Error Messages Files History ------- v2.x.x -- Irwin only support v3.0.0 -- Added Irwin Filemark/End-of-data support v3.1.0 -- Added Divergent track pattern and read-after-write verify v3.2.0 -- Added Conner SLC drive support but only for Irwin AccuTrak (not QIC) cartridges. v3.3.0 -- Added AIX-PS2 Irwin read only support. v4.0.0 -- Added Conner/Archive QIC support. Version 4.0.0a changes (relative to 3.3.0): o Conner/Archive QIC support added (including formatting). This includes the Hornet, Super Hornet, SLC, and Roadrunner. o Two choices for QIC write management: - SCO Xenix-Unix and Interactive Unix ft driver compatible (no filemark support), or - NT Posix compatible (filemarks allowed). o Read-after-write verify is NOT functional for QIC formats (if enabled, a console message is printed on first write to QIC tape after open()). o Alternate controller port/irq/dma is configured in "space.c". o The direct access device interface, used by previous versions, is no longer supported. However, tapes created by previous versions, can still be read and written. Version 4.0.0e: o Modified mc_link_most(), mc_link_least(), mc_move_most(), mc_move_least() to prevent kernel PANIC. Version 4.0.0f: o Modified read ahead code to ignore read data errors on close. This prevents incorrect "ECC verification error" on close. o Changed driver reported error on end-of-medium on writes from "Error 0" to "Tape full". Version 4.0.0k: o Increased interrupt priority level to fix random occurrences of mc: Read error 6 on tape unit 0: State machine hung o For tape management schemes which support filemarks, added automatic write filemark if data written, or skip to next to next filemark if data read on close. Version 4.0.0l: o Disabled auto-filemark support. Version 4.0.0m: o Re-enabled auto-filemark support. o Changed QIC write error recovery to decrement end-of-medium rather than end-of-data. This fixes incorrect reporting of "Not at beginning-of-tape or end-of-data" when data is being displaced by write error recovery. o Added 10 sector write error limit. Upon reaching this limit, the message "NOTICE: mc: Write error 107 on tape unit 0: Write error limit reached" is displayed on the console. Version 4.0.0n: o Changed error reporting on write error limit to report last actual error. o Recompiled all sources. Version 4.0.0o: o Fixed cause of system corruption and/or process hang during close after a write error. o After a write error, subsequent write attempts will now produce the message "NOTICE: mc: Write error 107 on tape unit 0: Write error limit reached" until the cartridge is reinserted or replaced. o Fixed incorrect reporting of "Error 0" rather than "ECC verification error" on read ECC verification error. Version 4.0.0p: o Fixed "no IRQ 7 interrupts" after mc driver initialization. o Added support for QIC 1000 foot cartridges. o Fixed "System hang during kernel initialization (at boot)" when certain SMC controllers are present (e.g, 37C932). The hang is caused by a failure to exit SMC configuration mode when, after entering, the part id is not recognized. o Added optional "Retension tape on first write after open". This feature is configured by mc_reten_write in space.c Version 4.0.0s: o Bug fix for position maintenance which caused the message "Not at beginning-of-tape or end-of-data" when appending Irwin or mgmt_qic_ntmark tapes using the no-rewind device. o Bug fix for inaccessibility of second tape backup when 'mcart rfm' is used to skip the first backup on Irwin or mgmt_qic_ntmark tapes accessed via the no-rewind device. o Changed Conner references to Seagate o Increased FDC fifo threshold from 4 to 11 to reduce DMA overruns. o On the first tape access, previous driver versions cause a tape application process to hang when the interrupt (IRQ) is incorrectly configured. This version exits and reports "92: Interrupt timeout". o Previous versions report "Block 0 medium defect" when the DMA channel is incorrectly configured. This version reports "17: DMA overrun". o Modified to prevent 'kernel panic' when used with alternate tape settings of DMA 2 and and an IRQ other than 6. Controller Support ------------------ In addition to the system floppy controller, the minicartridge (mc) driver v4.0.0 supports the following alternate floppy tape controllers: Seagate CTC-2Mb 2-Mbit (ISA) Conner CTC-2Mb 2-Mbit (ISA) Maynard 4100M 1-Mbit (ISA) Irwin 4100, 4100A, 4100C 1-Mbit (ISA) Irwin 4100MC 1-Mbit (MCA) Drive Support ------------- The minicartridge (mc) driver v4.0.0 supports the following floppy interface floppy tape drives: Seagate CTM420 (QIC-80, 8mm) Seagate CTT800 (QIC-80, 8mm, TR1) Seagate CTM700 (QIC-3010, 8mm) Seagate CTM1360 (QIC-3020, 8mm) Seagate CTT3200 (QIC-3020, 8mm, TR3) Seagate TapeStor 420 (QIC-80, 8mm) Seagate TapeStor 800 (QIC-80, 8mm, TR1) Seagate TapeStor 700/850 (QIC-3010, 8mm) Seagate TapeStor 1360/1700 (QIC-3020, 8mm) Seagate TapeStor 3200 (QIC-3020, 8mm, TR3) Conner 11250N/51250N (QIC-80) Conner CTM420 (QIC-80, 8mm) Conner CTT800 (QIC-80, 8mm, TR1) Conner CTM700 (QIC-3010, 8mm) Conner CTM1360 (QIC-3020, 8mm) Conner CTT3200 (QIC-3020, 8mm, TR3) Conner TapeStor 420 (QIC-80, 8mm) Conner TapeStor 800 (QIC-80, 8mm, TR1) Conner TapeStor 700/850 (QIC-3010, 8mm) Conner TapeStor 1360/1700 (QIC-3020, 8mm) Conner TapeStor 3200 (QIC-3020, 8mm, TR3) Archive Hornet 5540 (QIC-40) Archive Hornet 5580 (QIC-80) Archive SuperHornet 11250Q(1"), 31250Q(3.5"), 51250Q(5.25") (QIC-80) IBM Internal Tape Backup Unit (Similar to Irwin 285) IBM DualStor 250 Internal Tape Backup Unit (QIC-80) IBM DualStor 450 Internal Tape Backup Unit (QIC-80, 8mm) IBM DualStor 800 Internal Tape Backup Unit (QIC-80, 8mm, TR1) Irwin 110, 310, 410 (10 MB servo 0.15" DC1000) Irwin 120, 220, 320, 420, 720, 2020 (20/30 MB servo DC2080/DC2120) Irwin 125, 225, 325, 425, 725 (20 MB servo 0.15" DC1000) Irwin 145, 245, 345, 445, 745, 2040, A120 (40/60 MB servo DC2080/DC2120) Irwin 165, 265, 465, 765 (64 MB servo DC2080) Irwin 285, 485, 785, 2080, 287, 487, 787, 2120, A250 (80/120 MB servo DC2080/DC2120) Cartridge Support ----------------- The minicartridge (mc) driver v4.0.0 supports the following tape cartridges: mcart Capa- Format city Burst FRPI Tk*Blk Data+ECC Wide*Len Cartridge I10 10MB Irwin 6400 8*158 8+0 0.15"*185' DC1000 I20 20MB Irwin 6400 14*85 16+2 1/4"*205' DC2080 I20XL 30MB Irwin 6400 14*128 16+2 1/4"*307' DC2120 I25 20MB Irwin 10000 12*110 16+2 0.15"*185' DC1000 I45 40MB Irwin 10000 20*124 16+2 1/4"*205' DC2080 I45XL 60MB Irwin 10000 20*186 16+2 1/4"*307' DC2120 I65 64MB Irwin 13200 24*164 16+2 1/4"*205' DC2080 I85 80MB Irwin 11600 32*86 29+3 1/4"*205' DC2080 I85XL 120MB Irwin 11600 32*130 29+3 1/4"*307' DC2120 Q40 40MB QIC 10000 20*68 29+3 1/4"*205' DC2080 Q40XL 60MB QIC 10000 20*102 29+3 1/4"*307' DC2120 Q40PL 210MB QIC 10000 20*365 29+3 1/4"*1100' QDE2430 Q80 80MB QIC 14700 28*100 29+3 1/4"*205' DC2080 Q80XL 120MB QIC 14700 28*150 29+3 1/4"*307' DC2120 Q80 170MB QIC 14700 28*207 29+3 1/4"*425' DC2120XL or 400MB QIC 14700 28*~487 29+3 1/4"*1000' DC2120EX Q80PL 440MB QIC 14700 28*537 29+3 1/4"*1100' QDE2430 Q80W 220MB QIC 14700 36*~204 29+3 8mm *420' QW5122XLF or 400MB QIC 14700 36*~365 29+3 8mm *750' TR1 or 500MB QIC 14700 36*~487 29+3 8mm *1000' TR1EX Q3010 250MB QIC 22125 40*~215 29+3 1/4"*295' DC2500 or 340MB QIC 22125 40*~292 29+3 1/4"*400' MC3000XL Q3010W 430MB QIC 22125 50*~292 29+3 8mm *400' QW3010XLF or 800MB QIC 22125 50*~547 29+3 8mm *750' TR2 Q3020 500MB QIC 44250 40*~422 29+3 1/4"*295' DC2500 or 675MB QIC 44250 40*~572 29+3 1/4"*400' MC3000XL or 1600MB QIC 44250 40*~1431 29+3 1/4"*1000' MC3020EX Q3020W 850MB QIC 44250 50*~572 29+3 8mm *400' QW3020XLF or 1600MB QIC 44250 50*~1073 29+3 8mm *750' TR3 Note: ~ means approximate (Flexible format) Creating an Installation Floppy Diskette ---------------------------------------- Installation of the driver is accomplished by transferring the data image, contained in mc400s_i.Z, to an installation floppy diskette. 'sysadm' and 'kconfig' are then used to install the driver from floppy. The installation floppy diskette is a 3-1/2 inch, 135 tracks per inch, double sided, 18 sector per track (1.44MB) format. uncompress mc400s_i.Z - uncompress 'mc400s_i.Z' and convert it to a file named 'mc400s_i' . format /dev/dsk/f0q18dt - format a 1.44 MB 3-1/2" floppy diskette. cp mc400s_i /dev/dsk/f0q18dt - Copy the image file to the floppy. An installation floppy diskette is now prepared for use by 'sysadm'. You may want to write protect the floppy. Using sysadm and kconfig to Install the Minicartridge Driver ------------------------------------------------------------ Use -- sysadm -> Software -> Install a package -> disk0_1.44M -- to install the driver software on the hard disk. NOTE: If you encounter the message -- WARNING!! 'Irwin Floppy Tape - mini cartridge - Version 4.1' is already installed. [This is actually minicartridge Version 2.0.8a] Do you want to replace this package with Seagate/Irwin Minicartridge Floppy Tape - Version 4.0.0s? -- select 'YES' to replace. NOTE: If your system has an Adaptec 1542c with floppy drives attached and an alternate tape controller, the DMA channel setting needs to be changed from the default of DMA 2 to either DMA 1 or DMA 3. Both the controller's DMA jumpers (or switches) and the driver's DMA parameter must be altered. See "Alternate Tape Controllers" section below. To enable the driver use -- kconfig -> Configure -> Drivers Select the following entry and press mc N Seagate/Irwin Minicartridge Floppy Tape On the Driver Configuration Data screen, set the Driver Status to On -- Driver Status On Off (*) ( ) NOTE: Other Driver Configuration Data can be left at their initial settings: Type 0; Unit 1; IRQ 0; DMA Channel -1; Interrupt Priority Level 0; I/O Address Space Start 0, Stop 0; Controller Memory Ranges Start 0, Stop 0. Create a new kernel using with the newly installed driver using -- kconfig -> Build Install the kernel just built using -- kconfig -> Install Rebooting After Minicartridge Driver Installation ------------------------------------------------- After minicartridge driver installation, reboot the computer using the command: reboot 1) If rebooting with the new driver fails and hangs the system, then seek technical support. - In the meantime, the previous state of the system can be restored as follows: - Reset or re-power the computer and, quickly press at the message: Booting the INTERACTIVE UNIX Operating System... Then, when prompted for the name of a kernel, type: OLD.unix After the system comes up, as root: mv /OLD.unix /unix" mv /etc/conf/cf.d/OLD/* /etc/conf/cf.d - The driver may be removed from the kernel configuration using: kconfig -> Configure -> Drivers Select the following entry and press mc N Seagate/Irwin Minicartridge Floppy Tape On the Driver Configuration Data screen, set the Driver Status to Off -- Driver Status On Off ( ) (*) - Proceed to build and install kernel with the tape driver removed using: kconfig -> Build kconfig -> Install 2) Normally, during the boot process, the minicartridge driver displays the following banner: mc: minicartridge tape driver v4.0.0s - Immediately after displaying the banner, the driver searches for a tape drive. 3) If the following message is seen (after the above banner) -- mc: initialization error: 23: Drive not found - Wait for the system to prompt Console Login: - Login as root and run shutdown -g0 -y - When the following message is seen: The system is down. Press any key to reboot. Turn the power switch off. - Check that tape drive's data and power cables are properly connected and correctly oriented. "Correctly oriented" for the data cable means the, usually red, marked edge of ribbon cable corresponds to the pin 1 end of tape drive connector. When the power cable is correctly connected, Seagate, Conner, Irwin, and IBM tape drives will blink the LED (in the bezel) once shortly after power is applied. NOTE: It is recommended that a Seagate or Conner drive be configured for 'soft select' (This is the normally shipped configuration). - Power up the system and go to step 1 4) On successful boot, you may want to verify that the driver is functional by inserting a cartridge and using the following commands: mcart h Shows mcart command list mcart drive Shows driver information mcart info Shows tape cartridge information cd /usr/bin; tar cvbf 20 /dev/rctmini . Backup /usr/bin tar tvbf 20 /dev/rctmini Lists content of backup If you are using an alternate tape controller and, during tape access, one of the following messages is seen: "Drive not found", "Interrupt timeout", or "DMA overrun", go to the section "Alternate Tape Controllers" below. The "mcart" Utility ------------------- The minicartridge driver specific utility "/usr/lbin/mcart" has also been added to your system. It enables you to perform a number a useful functions on your tape drive. They are summarized below: h This is a help command which allows you to view a list of available "mcart" commands. drive This command provides information about drive type, controller type and unit select. info This command provides information about cartridge state, format and write protect slider position. capacity This command shows the total cartridge capacity in 512 byte blocks after formatting. kapacity This command shows the total cartridge capacity in 1024 byte blocks after formatting. format This command enables you to prepare unformatted tape cartridges for use with your tape drive. If you are using AccuTrak pre-formatted tape cartridges, you will not need to use this command. (SEE NOTE BELOW) To use the "format" command, you need to make sure you are using either brand new, unformatted tapes, or bulk (magnetically) erased tapes. rewind This command is used to rewind a tape after a backup or restore has been interrupted. Normally, the tape is rewound automatically. reten This command is used to align a tape that has not been used for a long time, or has been exposed to temperature extremes. The command syntax is: mcart command For example, using the "rewind" option, the command would be: mcart rewind No-rewind Device: /dev/mc/nrmc0 (For Advanced Users) ---------------------------------------------------- The no-rewind device, /dev/mc/nrmc0, was added to v4.x.x of the minicartridge driver. Using /dev/mc/rmc0 (rewind device), allows a single archive to be written to a given tape. Each time /dev/mc/rmc0 written, the previous archive is overwritten. Using /dev/mc/nrmc0 (no-rewind device), allows multiple archives to be saved to a single tape. Each archive is separated by a filemark. A filemark is a special (non-data) tape block automatically written on device close. *** WARNING: IN ORDER TO USE FILEMARKS ON QIC TAPES, THE DRIVER *** MUST BE CONFIGURED TO USE NT STYLE DEFECT/FILEMARK MANAGEMENT. For QIC tapes there are two choices for cartridge management either mgmt_qic_xenix or mgmt_qic_ntmark. mgmt_qic_xenix is compatible with the SCO Xenix-Unix ft driver and Interactive Unix xl driver. mgmt_qic_xenix has NO filemark support. mgmt_qic_ntmark uses Windows NT(tm) style filemark support. When reading tapes, the driver automatically recognizes either management style. When writing tapes, conversion from one defect/filemark management style to another takes place on the first tape write when tape is positioned at beginning-of-medium. A tape is at beginning-of-medium after cartridge insertion, after using the command "mcart rewind", or after using the rewind device /dev/mc/rmc0. The management style written can be selected at run time using the "mcart" utility. For example, use "mcart mgmt_qic_xenix" to select Xenix/Unix ft/xl driver compatible (no-filemarks) QIC management, or "mcart mgmt_qic_ntmark" to select NT (filemark support) QIC style management. Better yet, the initial management selection may be changed by editing the value in mc_mgmt_qic in /etc/conf/pack.d/mc/space.c and re-linking the kernel. Current management values (applied when writing tape from beginning- of-medium) are displayed by the command "mcart mgmt". The minicartridge tape driver will only allow writing tape positioned to beginning-of-medium or end-of-data. When using /dev/mc/nrmc0, the following mcart commands are useful: mcart rewind Positions read/write pointer to beginning-of-medium. mcart eod Positions read/write pointer to end-of-data. mcart rfm Positions read/write pointer just past next filemark If no more filemarks present, positions to end-of-data. Notes ----- (1) Due to problems arising while formatting tapes and for data integrity reasons, it is highly recommended that pre-formatted tapes be used. The format option is provided for use at your own risk! (2) If you choose to format your own tapes, remember that you MUST BULK ERASE the tape to be formatted. If you do not bulk erase your tape, you will not be able to format it. Please remember that the format option is *not* fully supported. It is provided for use at your own risk! (3) Normally, the device you write to should be "/dev/mc/rmc0". This device needs to be specified regardless of whether you are writing to the drive with "tar", "backup", "cpio", or some other utility. (4) While installing your hardware, please refer to the hardware guide shipped with your tape backup unit. If you have questions regarding the installation of your hardware, contact Seagate Technical Support. (5) After installation, additional documentation is present in the file /usr/lib/tape/mc.txt Alternate Tape Controllers -------------------------- At boot time, the driver scans for tape drives. First an alternate controller is scanned and then the system controller. See "Controller Support" section above for a list of alternate tape controllers. The system floppy controller uses these fixed settings: System Floppy Controller (SYSFDC) Settings Base I/O Port: 3F0 (hexadecimal) Interrupt Request (IRQ): 6 DMA Channel: 2 The driver default parameters for an alternate tape controller are: Alternate Tape Controller (ALTFDC) Default Settings Base I/O Port: 370 (hexadecimal) Interrupt Request (IRQ): 6 DMA Channel: 2 The driver's default parameters correspond to the standard settings of the Irwin 4100, Maynard 4100M, and Seagate/Conner CTC-2Mb controllers. Thus, in the default configuration, the alternate controller shares IRQ 6, and DMA 2, with the system floppy controller. When, IRQ and/or DMA settings are shared, the driver manages IRQ/DMA switching and diskette/tape contention. If the following message is seen on the first tape access when an alternate tape controller is used, "DMA overrun", possible causes are: 1) The DMA channel jumpers on the controller may not match the DMA channel settings in the driver's configuration. The solution is to reconfigure the alternate tape controller board and/or driver DMA setting to match. 2) There may be a DMA conflict with another board in the system. If DMA 2 is configured, the system floppy controller may be failing to disconnect from the bus. This condition is typical in a system which uses the Adaptec 1542c SCSI/Floppy controller for the floppy drives. The resolution is to reconfigure both the board jumpers and driver setting for another DMA channel (usually DMA 1 or 3). 3) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have 2 DMA jumpers or 2 switches that need to be set to the "on" position. Switches, in particular, can become corroded. If they are supposed to be in the "on" position, try cycling them "off" then back "on" a couple of times. 4) The system DMA controller (on the system board), may be defective. If the following message is seen on the first tape access when an alternate tape controller is used, "Interrupt timeout", possible causes are: 1) The IRQ setting of the alternate tape controller may not match the configuration of the driver. The solution is to reconfigure the alternate tape controller board IRQ jumper and/or driver IRQ setting to match. 2) The IRQ setting of the alternate tape controller may conflict with another controller. The resolution is to reconfigure both the board IRQ jumper and driver IRQ setting for a different interrupt request. 3) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have an IRQ jumper or a switch that needs to be set to the "on" position. Switches, in particular, can become corroded. If it is supposed to be in the "on" position, try cycling it "off" then back "on" a couple of times. If the following message is seen on system boot or when attempting to use the tape drive: "Drive not found", possible causes are: 1) The tape drive may be defective or may not be receiving power from the red-black-black-yellow power cable. For Seagate, Conner, Irwin, and IBM tape drives the LED should light briefly when the system is first powered. Check for a secure power cable connection. Power cycle the system and see if the LED flashes. 3) The tape drive's "select" jumper, if any, may be improperly set. Consult hardware manual for the jumper setting. Typically, if a drive supports it, "soft select" is recommended. 2) The ribbon cable may defective or may be misaligned at either the controller or tape drive connectors (pin 1 on the connectors must match), or the ribbon connectors may not be fully inserted. Check ribbon cable installation. 3) The I/O port and/or IRQ settings of the alternate tape controller may not match the configuration of the driver. The solution is to reconfigure the alternate tape controller board I/O port and IRQ jumpers and/or driver I/O port and IRQ settings to match. 4) The I/O port and/or IRQ settings of the alternate tape controller may conflict with another controller. The resolution is to reconfigure both the board jumpers and driver settings for a different I/O port and/or IRQ. 5) The alternate tape controller may be defective or not well seated in its slot. Try re-inserting the controller or moving it to another slot. Most alternate tape controllers have an jumper or switches to select the I/O port. Switches, in particular, can become corroded. If they are set to the "on" position, try cycling them "off" then back "on" a couple of times. The driver's "Alternate controller" settings may be configured by editing /etc/conf/pack.d/mc/space.c. Use a text editor such as vi (for example, vi /etc/conf/pack.d/mc/space.c) and adjust the values for: int mc_altfdc_port = 0x370; int mc_altfdc_irq = 6; int mc_altfdc_dmachan = 2; Notes: In "int mc_altfdc_port = 0x370;", the '0x' means that 370 is hexadecimal (omitting 0x makes it decimal). If "int mc_altfdc_port = 0;" the alternate controller drive search is disabled. After editing space.c, the kernel must be rebuilt, installed, and the system rebooted for changes to take effect. Use /etc/kconfig to rebuild and install a new kernel. Error Messages -------------- Below is a list of the most common error messages included in the minicartridge (mc) tape driver. Block not found IE_BLKNOTFND(5) --------------- A block not found error occurs when the driver cannot locate a physical tape block during a read or write operation. Insure the tape head is clean (see the tape drive hardware manual for cleaning instructions). When this message is displayed during a data restore operation, try retensioning the tape, then repeat the restore operation. If this fails, try restoring the data using a different tape drive. When this message is displayed during data backup operation, try another tape. If your backup is successful on another tape, discard or bulk erase and reformat the original tape. Data CRC error IE_CRC(12) ID CRC error IE_IDCRC(13) -------------- An "ID CRC error", or "Data CRC error" message is displayed during a tape read operation when a tape block cannot be recovered by ECC. If this message appears, retension the tape and try again. If this fails, the data might be recovered by using a different tape drive. Causes of persistent CRC errors are: poor quality tapes, worn tape head, a defect in the drive's record circuitry, or an incompatible or otherwise defective data separator circuit on the controller. CRC errors might be stopped by using new tapes, or installing a data compensator circuit on the drive. Record not found IE_RECNOTFND(14) ---------------- A "Record not found" error occurs when some sector within a tape block cannot be located. This error typically occurs on a during a tape read operation when there are too many erroneous sectors to recover data using ECC. (See Data CRC Error) Drive not found IE_DRVNOTFND(23) --------------- During system boot, a drive searching algorithm is executed by the driver. If this algorithm fails to detect the presence of a tape drive, "mc: initialization error: 23: Drive not found" is displayed. Subsequently, a similar message is displayed on any read or write access to an opened MC device file for which no drive is present. When this message appears, hardware should be checked. Make sure that data and power cables are connected and correctly oriented. "Correctly oriented" for the data cable means the, usually red, marked edge of ribbon cable corresponds to the pin 1 end of tape drive connector. When the power cable is correctly connected, Seagate, Conner, Irwin, and IBM tape drives will blink the LED (in the bezel) once shortly after power is applied. Servo failure IE_SERVO(24) ------------- "Servo failure" is a tape formatting error message. The servo writing function is a part of the tape drive's firmware. The driver commands the tape drive to servo write and awaits tape drive completion status. Usually the drive's LED will be flashing on servo writing failure. Try bulk erasing the cartridge and restart the format. If this fails, try another cartridge. Insufficient memory IE_NOMEM(42) ------------------- "Insufficient memory" messages are given when the driver fails to allocate at least three tape block buffers. Sufficient memory may be available when single user mode is entered immediately after system boot. Usually adding memory to the system will stop this message. Block 0 missing servo header IE_SERVOBLK0(43) Too many sequential missing servo headers IE_SERVOSEQ(44) Too many missing servo headers on track IE_SERVOTRK(45) Too many missing servo headers IE_SERVOTOT(46) Too many sequential bad blocks IE_CYLSEQ(47) Too many bad blocks on a track IE_CYLTRK(48) Too many bad blocks IE_CYLTOT(49) ----------------------------------------- These messages occur during formatting. When formatting fails for one of these reasons, try bulk erasing the cartridge and re- formatting. If this fails, try another cartridge. Block 0 medium error IE_BLK0DEFECT(52) -------------------- A "Block 0 medium error" results when, during tape state determination, the first tape block has a medium error which is not recoverable by either redundant correction or ECC. Normally the cartridge should be reformatted or discarded. If the cartridge has a backup on it, try using a different drive to read the tape. If this message persists for multiple cartridges, the tape drive's read circuitry may be out of adjustment, or there may be an incompatibility between the floppy controller's data separator circuit and the tape drive. Defect list has unrecoverable error IE_DLISTDEFECT(54) ----------------------------------- This message is displayed when both copies of the relocation table (kept in the second and third good tape blocks) have unrecoverable medium errors or are otherwise corrupt. Defect list corrupt IE_DLISTCORRUPT(55) ------------------- This message is displayed if an error is found in the primary defect list kept in block 0. Reformat the tape. Interrupt timeout IE_INTRTMO(92) ------------------- An "Interrupt timeout" occurs when an interrupt is not received from the floppy tape controller. If this error is seen during initialization or the first access of the tape drive, it may be caused by: 1) incorrect driver interrupt (IRQ) configuration, 2) incorrect floppy tape controller interrupt (IRQ) configuration (usually set by jumper on the controller board), or 3) another board configured for the same interrupt (IRQ) as the floppy tape controller (a hardware interrupt conflict). See "Alternate Tape Controllers" above. Files ----- /etc/conf/pack.d/mc/DrivDesc /etc/conf/pack.d/mc/Driver.o Driver object /etc/conf/pack.d/mc/space.c Driver configuration source /etc/conf/node.d/mc Node definitions for /dev directory /etc/conf/sdevice.d/mc System device configuration /etc/conf/cf.d/mdevice Master device list /usr/lib/tape/mc.txt Documentation /usr/lbin/mcart Driver specific command utility /dev/mc/rmc0 Rewind tape device (minor=0) /dev/mc/nrmc0 No-rewind device (minor=4) /dev/rctmini Rewind device (minor=0) /dev/nrctmini No-rewind device (minor=4) /dev/xctmini Control device (minor=4)